Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add parameter to optionally disable the publication of the static tf #330

Conversation

doisyg
Copy link

@doisyg doisyg commented May 25, 2024

Related Issues & PRs

Summary of Changes

This PR adds the parameter pub_static_tf, by default True, to control if the user wants or not to have the driver node publishing the static transform between the sensor frames.
It is useful to have it disabled in systems where a calibration process directly modifies the tf of the point cloud frame.

Validation

@nachovizzo
Copy link

@Samahu it would be great if we could discuss moving forward with this PR as it allows to have a little bit more control over how to manipulate the static transformations of the 3 different ouster coordinate frames

@Samahu
Copy link
Contributor

Samahu commented Oct 25, 2024

@nachovizzo Sure, I will prioritize the merge of @doisyg work within couple days

@Samahu Samahu self-requested a review October 25, 2024 21:02
@Samahu Samahu changed the base branch from ros2 to ROS2-389-replay-improvments-and-fixes October 30, 2024 00:52
Copy link
Contributor

@Samahu Samahu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merging into a branch/PR so I can add expose the new parameter to config

@Samahu Samahu merged commit 075378a into ouster-lidar:ROS2-389-replay-improvments-and-fixes Oct 30, 2024
3 checks passed
@Samahu Samahu added the enhancement New feature or request label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants